Kenexa     Kenexa XML Integrations                                                     

 

 

 

Job Code Default Data Integrations:

Job codes and their associated requisition information can be imported from an external system into Kenexa Recruiter BrassRing.

Job codes allow an organization to maintain a list of standard job titles, descriptions, and associated codes for advertising. They can also be used to pre-populate default data into reqs.

Special Instruction for Job Code Default Data Integrations

1. Unlike other types of Foundation data, Position data (Job Code) must be uploaded one at a time, thus only one packet per envelope

2. JobCode is used as a record key identifier.

3. JobCodeDesc and Job_Title are stored in two distinct places on the Kenexa Recruiter BrassRing requisition form. The values for these fields are usually the same but can be different based on a client’s specific configuration.

4. Job Code Status must be either “A” (active) or “I” (inactive).

5. <JOBCODE>, <JOBCODEDESC>, and <JOBCODESTATUS> tags are the only required tags for Position Data upload. All additional tags are optional and map to client’s specific requisition form fields.                                                                                                                      6. The JOBOO node may be included with Position Data.  See Notes for Requisition Import for more information.

7. Language may be specified as an attribute.  For example, <POSITIONDATA language=”GB”> will attach the job code to International English.  <POSITIONDATA language=”DE”> will attach the job code to German.  If no language attribute is included, then KRB will attach the default language.

 

Sample XML 

 

<?xml version="1.0"?>

<Envelope version="01.00">

       <Sender>

             <Id>HRISUSER</Id>          <!-- Configured for a Client - Integration User - this information does not change once Kenexa provides -->

             <Credential>100</Credential>         <!-- Configured for a Client - Client ID - this information does not change once Kenexa provides -->

       </Sender>

       <Recipient>

             <Id/>

       </Recipient>

       <TransactInfo transactType="data">

             <TransactId>5555</TransactId>                        <!-- This is for tracking purpose for use to the Client only. It can be numeric or alphanumeric -->

             <TimeStamp>2006-02-28 09:22:10AM</TimeStamp>    <!--date-time value for troubleshooting and tracking -->

       </TransactInfo>

       <Packet>

             <PacketInfo packetType="data">

                    <PacketId>1</PacketId>

                    <Action>SET</Action>

                    <Manifest>POSITIONDATA</Manifest>

             </PacketInfo>

             <Payload><![CDATA[<?xml version="1.0"?>

       <POSITIONDATA>

             <!--Standard Fields. These fields are required fields -->

             <JOBCODE>NU016</JOBCODE>  

             <JOBCODEDESC>IT Sourcing Director</JOBCODEDESC>

             <JOBCODESTATUS>A</JOBCODESTATUS>

 

                       <!--Examples of Custom Fields - Depends on the fields on your Req Forms-->

             <JOB_DESCRIPTION>.</JOB_DESCRIPTION>

             <EXEMPT_NONEX>Exempt</EXEMPT_NONEX>

             <JOB_FAMILY>Administration</JOB_FAMILY>

             <AAP_JOBFAMILY>1Z</AAP_JOBFAMILY>

             <BUSINESS_UNIT>USFS</BUSINESS_UNIT>

             <EEO1>1</EEO1>

       </POSITIONDATA>

       ]]></Payload>

       </Packet>

</Envelope>

© 2008 Kenexa